IDeaL Creative

Case Study — Chapter One

Floor & Décor

Rebuilding a training library's information architecture, governance, and site experience so 10,000+ associates could trust what they found.

The problem

A centralized library of multimedia and technical training resources, supporting a program reaching associates across eight retail departments — sitting on SharePoint Classic, with no naming standard, no lifecycle rules, and no reliable way to tell a current document from an abandoned one.

The visible symptom was that people could not find things. The real cost was quieter: field teams had stopped trusting the library, so they made their own copies. Every local copy was another version drifting away from the source, and no one could say which was authoritative.

300+
multimedia & technical resources
10,000+
associates supported
8
retail departments

What I built

Six workstreams, from evidence to governance to the pages themselves.

Content audit

A full inventory of the library, classified by currency, ownership, usage, and duplication. The audit was the argument: you cannot get a governance decision approved on principle, but you can get one approved on evidence.

Naming conventions

A consistent naming standard for course content and resources, designed so a filename alone communicates type, audience, department, and version. Retrieval works before search does.

Content lifecycle management

Explicit rules for creation, review, revision, archive, and retirement, with named owners and review cadences. Content that nobody owns is content that nobody updates.

Information architecture & migration

Restructured taxonomy and navigation, then migrated the full library from SharePoint Classic to Modern against the new architecture rather than porting the old mess forward.

Site page build-out & UX design

Designed and built the site pages themselves: navigation hierarchy, landing page structure, page-level layout, and wayfinding. Site map design was a deliberate exercise, documented and validated with stakeholders before build.

Learning team governance documentation

Workflows, roles, decision rights, intake process, and resource standards, documented as a working reference the team could actually operate from after I stopped being in the room.

]]>